Purpose

The primary goal of this pull request is to enhance the ui-export-manager by introducing support for exporting claims. This functionality is essential for users who need to manage and export claim data efficiently within the FOLIO platform.

https://folio-org.atlassian.net/browse/UIEXPMGR-113
https://folio-org.atlassian.net/browse/UIEXPMGR-114

Approach

• Implementation of Claims Export Functionality:

  • Introduced new logic to handle the export of claims, ensuring that the feature integrates seamlessly with existing export functionalities.

• Optimization of CQL Query Construction:

  • Updated the logic for building CQL queries to improve performance and maintainability. This includes:
    • Grouping and deduplicating CQL conditions by their keys and values.
    • Ensuring reliable alphabetical sorting of keys using String.localeCompare for consistent query generation.
    • Minimizing the size and complexity of generated queries while preserving their correctness.

Screenshot

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

• I've added appropriate record to the CHANGELOG.md
• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

• What other modules will these changes impact?
• Do JIRAs exist to update the impacted modules?
  • If not, please create them
  • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
  • Do they have all they appropriate links to blocked/related issues?
• Are the JIRAs under active development?
  • If not, contact the project's PO and make sure they're aware of the urgency.
• Do PRs exist for these changes?
  • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.